Not sure how to handle hopsworks-api move from "storage connector" to "data source".
Maybe we should have left storage connector naming as it was and just add data source functionality for creating external feature groups (that is also how it works in the back end).
Ill think how this can be accommodated, but probably now ill have to create new classes/methods and deprecate the old ones + see how to handle naming overlaps since feature group already has "data_source" variable and it only specifies data access not auth etc. (like storage connector does)